Component org.nuxeo.ecm.core.blob.BlobManager
In bundle org.nuxeo.ecm.core.api
Documentation
Blob Manager, delegating logic to the appropriate Blob Provider.
Resolution Order
117
The resolution order represents the order in which this component has been resolved by the Nuxeo Runtime
framework.
You can influence this order by adding "require" tags in your component declaration, to make sure it is resolved after another component.
Start Order
817
The start order represents the order in which this component has been started by the Nuxeo Runtime framework.
This number is interesting to tweak if your Java component interacts with other components, and needs to be started before or after another one.
It can be changed by implementing the method "Component#getApplicationStartedOrder()" on your Java component: components are sorted according to this reference value, in increasing order.
The default value is 1000, and the repository initialization uses number 100. Negative values can also be used.
Implementation
Class:
org.nuxeo.ecm.core.blob.BlobManagerComponent
Services
Extension Points
Contributions
XML Source
<?xml version="1.0"?>
<component name="org.nuxeo.ecm.core.blob.BlobManager" version="1.0.0">
<documentation>
Blob Manager, delegating logic to the appropriate Blob Provider.
</documentation>
<implementation class="org.nuxeo.ecm.core.blob.BlobManagerComponent" />
<service>
<provide interface="org.nuxeo.ecm.core.blob.BlobManager" />
</service>
<extension-point name="configuration">
<documentation>
Extension points to register the blob providers.
</documentation>
<object class="org.nuxeo.ecm.core.blob.BlobProviderDescriptor" />
</extension-point>
<extension target="org.nuxeo.runtime.ConfigurationService" point="configuration">
<documentation>
Delay before a blob which has had its digest computed asynchronously is deleted.
@since 2021.9
</documentation>
<property name="nuxeo.blobmanager.delete.delay">1h</property>
</extension>
</component>